Controller Protocols

With a Controller selected, choose the Protocols tab which is also available from the Patch window:

Depending on the Controller type selected, the Protocols tab allows you to configure the available eDMX A shorthand term for DMX-over-Ethernet protocols, for example Art-Net. and other output protocols:

Network 2 (Protocol)

MTPC, MSC 1, 2 & 4

Though the MTPC and MSC 1, 2 & 4 only have a single Ethernet port, this port may be configured with two IP addresses - one for management data and the other for output protocol data. The default setting is for this dual IP mode to be disabled, so that the same IP settings are used for management and output protocol data. Dual IP mode is particularly useful for working with KiNET power supplies, which must use 10.xx.xx.xx addresses.

The Network 2 virtual port can be configured with a VLAN tag to route the data to the relevant VLAN when used managed networks and VLANs to separate the Management and Data networks within the network infrastructure.

DMX Proxy (MSC 1 only)

If a Designer project has a MTPC and an MSC 1, the MTPC can output local DMX via the MSC's second DMX port. With the MSC 1 selected, choose the MTPC from the drop down list.

Art-Net output customisation

By default, a controller with less than 30 universes of Art-Net patched will broadcast all data until a device requests unicast for a specific universe. Controllers with more than 30 Art-Net universes patched will only unicast data to devices requesting universe data and will not automatically broadcast.

There is the option to 'Disable Broadcast' for a controller. The controller will still unicast data to devices that request it. There is also the option to 'Always Broadcast' on a per universe basis. This will force the controller to always broadcast that universe's data. 'Always Broadcast' will override the 'Disable Broadcast' option.

Within the Protocol Properties, is the option to enable Art-Net Sync, which can be used to ensure multiple Art-Net receivers stay in sync (if they are capable of receiving this)

KiNET Output Customisation

Within the Protocol Properties, is the option to enable KiNET Sync, which can be used to ensure multiple KiNET receivers stay in sync (if they are capable of receiving this)

eDMX Pass-Through

When using an MSC family controller in a project it is possible to allow eDMX from another eDMX source to be passed through to the controller’s outputs. This can be local DMX ports on the controller, the ports on a MSC-NET Mk3.

With anMSC family controller selected, select the 'Protocols' tab from the properties pane and click 'Manage' under 'eDMX Pass-Through' to configure eDMX Pass-Through buses.

From here, click 'New' to add a new bus, and select the eDMX protocol and universe that bus should treat as its source. You can also configure the bus with a name and number.

To assign an eDMX Pass-Through bus to an output, go to Patch and select the desired bus from the drop-down next to 'Protocol Pass-Through' above the patch sheet for the universe you wish to pass-through to.

There is also the option to auto-revert to the project’s output if eDMX isn't received for a specified amount of time.

eDMX pass-through is enabled and disabled using Triggers.

Note that only Art-Net and sACN are supported for eDMX Pass-Through.

IMPORTANT: Changes made to a Controller's protocols will only take effect after an upload.

eDMX Pass-Through Merge

If sACN is being used for eDMX Pass-Through and multiple sources are received, the controller will use the Source with the Highest priority.

If multiple streams are received with the same priority:

If there are exactly 2 streams, the controller will do a HTP merge (per channel). Meaning the highest level for each channel from either source will be used.
If more than 2 sources are received, then all streams are dropped.